|
|
|
|
|
|
|
learned specifically how to incorporate in the design models new discoveries in the way the end user uses your VB application. Moreover, you gained insight into preserving the artifacts of use-case analysis and development in general. Finally, you acquired knowledge toward assessing terminology and traceability, including domain-specific terminology for the Samsona Bank Teller example and related traceability issues involved in refining use cases. |
|
|
|
|
|
|
|
|
Then you learned the basics of the Graphical User Interface Subsystem. Specifically, you learned how to use the modeling techniques for GUIs and understood the encapsulation of data presentation into a separate class. Finally, you became familiar with some ideas behind ergonomics and internationalization with resource files. |
|
|
|
|
|
|
|
|
On the next day, you learned how to implement a Graphical User Interface Subsystem. You placed the core logic you generally insert in forms into classes that control the interaction between the forms and the rest of the application. You became familiar with the Facade design pattern, which is a role that can be played by both the form and the controller class. Finally, you received detailed treatment for incorporating the Graphical User Interface Subsystem into the Samsona Bank Teller System example. |
|
|
|
|
|
|
|
|
On Day 13, The Workgroup and User Security Subsystem, you learned about the Workgroup and User Security Subsystem. In particular, you learned the purpose of this necessary subsystem and related security issues, including a class for encrypting the password instead of relying solely on asterisk characters. Then you incorporated the subsystem into the Samsona Bank Teller System example. |
|
|
|
|
|
|
|
|
On the last day of the week, the concept of the Internal Application Manager is used as a mechanism for controlling the initializing and terminating of the application, as well as managing the states an application goes through during a typical session. In particular, you learned the use of an encrypted settings file for more secure applications. Then you studied logging as a way to create a history of user interactions with the application, errors and exceptions, and memory allocations/deallocations. |
|
|
|
|
|